fix(build): distinct artifact names for nsis vs portable exe#14
Merged
Conversation
Both Windows targets emitted Hatchling-<version>-x64.exe — the portable build overwrote the installer during release publishing and the duplicate upload broke the workflow. Name them -setup- and -portable- respectively.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The v1.0.0 release run: Windows built both targets fine, but nsis and portable share
.exe, so both emittedHatchling-1.0.0-x64.exe— the portable upload overwrote the installer on the draft release, then the duplicate-upload dance timed out and failed the job (Linux/mac published clean). Distinct names:-setup-/-portable-.CI covers lint/typecheck/test/build; the release path re-verifies via workflow_dispatch after merge.